Indicating radio bearer information to network applications

ABSTRACT

Providing information related to a quality of a mobile communication link to an internal and/or external application provider is described herein. By way of example, a system can include component(s) that can receive communication link quality information associated with a mobile session, incorporate such information into a data packet, and forward such data packet to an application provider. The system can provide such information for second generation network components, third generation network components, and advanced components compatible with both second and third generation network architectures.

RELATED APPLICATION

This non-provisional patent application is a continuation of, and claimspriority to U.S. patent application Ser. No. 13/684,898, filed Nov. 26,2012, and entitled, “INDICATING RADIO BEARER INFORMATION TO NETWORKAPPLICATIONS,” which is a continuation non-provisional applicationclaiming priority to U.S. patent application Ser. No. 11/738,145, filedApr. 20, 2007, and entitled, “INDICATING RADIO BEARER INFORMATION TONETWORK APPLICATIONS,” which is a non-provisional application claimingpriority to U.S. Provisional Application No. 60/894,009 filed Mar. 9,2007, entitled INDICATING RADIO BEARER INFORMATION TO NETWORKAPPLICATIONS, the entireties of which applications are herebyincorporated herein by reference.

BACKGROUND

Third generation partnership project (3GPP) mobile communicationstandards are being implemented worldwide to effectuate a globaltransition from a mobile voice communication architecture to a voice anddata communication architecture. Such standards can typically specify,for example, data transfer protocols, wireless radio frequency ranges,roaming standards and protocols, mechanisms for transferringbilling-related information, etc. Many concurrent standards are requiredto effectuate communication amongst the various existing communicationarchitectures (e.g., second generation (2G), data-capable secondgeneration (2.5G), third generation (3G), etc.), and until transition toa single mobile architecture is fully established, the disparatestandards and multi-mode mobile devices incorporating such standardsmust be maintained. Consequently, network protocols bridgingcommunications between such devices and various compatible networkarchitectures must also be maintained. For example, a multi-mode devicethat can transition between a 2G, 2.5G, and 3G network requirescommunication protocols that facilitate transfer amongst those networks.In addition, because transfer could be necessary during a communicationsession, such protocols should facilitate network transfer both in andout of a session.

A typical problem that arises as a result of network transfer relates tomanaging data exchange compatible with one network architecture ascompared with a second architecture. For instance, a first networkarchitecture can specify a particular quality of service applicable tocommunication with devices, whereas a second network architecture mightbe a ‘best effort’ network, which cannot provide quality of serviceguarantees. Yet to maintain reliable communication, a network serviceprovider must find a mechanism to bridge a gap between establishednetworks that can provide quality of service guarantees and newernetworks, highly desired due to advanced technological capabilities,which are still developing an infrastructure necessary for suchguarantees.

Differing communication protocols can affect application contentproviders that incorporate network applications related to network mediatransfer. Examples of such network applications include streaming videoapplications, streaming audio applications, Internet access andinterface applications, ring-tone applications facilitating downloadingof ring-tones to mobile devices, and like applications. Networkapplications, whether supplied by a communication network provider or athird-party entity, must also transition amongst varying data exchangeparameters (e.g., packet transmission bit-rate, bandwidth, priority,error-rate, etc.) required by differing networks as devices roam fromone network architecture to another. Doing so smoothly and efficientlycan help facilitate desired quality of service guarantees fortechnologically advanced networks, analogous to guarantees provided byestablished, conventional networks.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 depicts an example high-level block diagram of a system that canidentify and provide a mobile communication link quality in accord withvarious aspects of the claimed subject matter.

FIG. 2 illustrates an example high-level block diagram of a system thatcan transmit mobile communication link quality information to aninternal or external application.

FIG. 3 depicts a sample block diagram of a mobile device that can detectand provide a communication link quality or change in such quality inaccord with aspects of the claimed subject matter.

FIG. 4 illustrates a sample block diagram of a system that can detectchanges in communication link quality associated with a mobile deviceand broadcast contemporaneous link quality in accord with variousaspects of the claimed subject matter.

FIG. 5 illustrates an example block diagram of a system that can detect,update and store communication link quality information in accord withvarious aspects disclosed herein.

FIG. 6 illustrates a block diagram of an example system that providesnetwork architecture information associated with a mobile communicationlink to an application content provider in accord with particularaspects disclosed herein.

FIG. 7 depicts an example block diagram illustrating transfer protocolsbetween various system components in conjunction with aspects of theclaimed subject matter.

FIG. 8 illustrates an example methodology for providing mobile networklink information applicable to network transfer applications in accordwith aspects of the subject innovation.

FIG. 9 illustrates a sample methodology for providing application dataexchange appropriate for a mobile network link in accord with thedisclosed subject matter.

FIG. 10 illustrates a sample methodology for indicating networkarchitecture information associated with a mobile communication inaccord with aspects disclosed herein.

FIG. 11 depicts an example computing environment applicable todetecting, updating and/or transferring network information in accordwith aspects of the claimed subject matter.

FIG. 12 illustrates a sample networking environment that can effectuatemobile communication and can facilitate data transfer applications inaccord with various aspects of the subject disclosure.

Appendix A discloses various aspects of the claimed subject matter andis hereby incorporated into the subject specification.

DETAILED DESCRIPTION

The subject matter is now described with reference to the drawings. Inthe following description, for purposes of explanation, numerousspecific details are set forth in order to provide a thoroughunderstanding of the claimed subject matter. It can be evident, however,that such matter can be practiced without these specific details. Inother instances, well-known structures and devices are shown in blockdiagram form in order to facilitate describing the claimed subjectmatter.

As used in this application, the terms “component” and “system” areintended to refer to a computer-related entity, either hardware, acombination of hardware and software, software, or software inexecution. For example, a component can be, but is not limited to being,a process running on a processor, a processor, a hard disk drive,multiple storage drives (of optical and/or magnetic storage medium), anobject, an executable, a thread of execution, a program, and/or acomputer. By way of illustration, both an application running on aserver and the server can be a component. One or more components canreside within a process and/or thread of execution, and a component canbe localized on one computer and/or distributed between two or morecomputers.

Furthermore, the claimed subject matter may be implemented as a method,apparatus, or article of manufacture using standard programming and/orengineering techniques to produce software, firmware, hardware, or anycombination thereof to control a computer to implement the disclosedsubject matter. The term “article of manufacture” as used herein isintended to encompass a computer program accessible from anycomputer-readable device, carrier, or media. For example, computerreadable media can include but are not limited to magnetic storagedevices (e.g., hard disk, floppy disk, magnetic strips, and the like),optical disks (e.g., compact disk (CD), digital versatile disk (DVD),etc.), smart cards, and flash memory devices (e.g., card, stick, keydrive, and the like). Additionally it should be appreciated that acarrier wave can be employed to carry computer-readable electronic datasuch as those used in transmitting and receiving electronic mail or inaccessing a network such as the Internet or a local area network (LAN).Of course, those skilled in the art will recognize many modificationsmay be made to this configuration without departing from the scope orspirit of the claimed subject matter. Moreover, the word “exemplary” isused herein to mean serving as an example, instance, or illustration.Any aspect or design described herein as “exemplary” is not necessarilyto be construed as preferred or advantageous over other aspects ordesigns.

Communication link properties are provided, associated with acommunication between a mobile device and a communication network, to anapplication content/service provider. Such properties can be used tofacilitate an application data exchange appropriate for a mobileconnection quality. For example, if an application provider is notifiedthat a particular network link allows for a certain data transmissionbandwidth, the provider can ensure that a streaming video applicationtransfers data to the device at a rate substantially similar to thatbandwidth. Additionally, information relating to a network architecturetype (e.g., a data-capable, relatively moderate bandwidth, secondgeneration (2.5G) and/or relatively high bandwidth third generation (3G)network) associated with a mobile link can be forwarded to a networkgateway, embedded within a portion of a communication data packet, andforwarded to an application content/service provider. Forwarding networkarchitecture information to an application content/service provider canbe sufficient to indicate communication link properties associated witha mobile communication. Consequently, such provider can operate anapplication in a manner appropriate for data exchange via conventionalnetworks, or take advantage of high quality service provided by advancednetworks.

Detecting a change in communication link quality and broadcasting suchchange to application content/service providers is also provided. Suchaspects enable an application content/service provider tocontemporaneously adjust application data exchange between a mobiledevice and a communication network according to a concurrentcommunication link quality. More specifically, a detection component candetermine a change in communication link quality (e.g., caused byhandover from a third generation (3G) communication network to adata-capable second generation (2.5G) communication network, or viceversa) and forward the determination to a gateway component. The gatewaycomponent can provide this determination to an applicationcontent/service provider (e.g., a third-party streaming videoapplication provider) by modifying a data packet so as to indicate suchchange in communication link quality, and forwarding the data packet tothe application content/service provider. Accordingly, an applicationcontent/service provider is not required to monitor a network or amobile device in order to provide an application data exchangeappropriate for a concurrent communication link quality.

Systems and methods are also provided that can store communication linkinformation associated with multiple communications links between one ormore networks and one or more mobile devices. Components associated withthe systems and methods can detect communication link qualityinformation and/or change in quality information (e.g., caused byroaming from an advanced to a conventional network architecture, causedby increase in neighboring traffic or network interference, etc.) andupdate a storage component with the quality information. An applicationcontent/service provider can access such stored quality information todetermine an appropriate parameter (e.g., bandwidth) applicable to adata exchange related to an application. Consequently, applications thatdo not interpret data packets modified to include such information canstill provide an application data exchange appropriate for a particularcommunication link quality.

To the accomplishment of the foregoing and related ends, certainillustrative aspects are described herein in connection with thedescription herein and the annexed drawings. These aspects areindicative, however, of but a few of the various ways in which theprinciples disclosed herein can be employed and is intended to includeall such aspects and their equivalents. Other aspects and novel featureswill become apparent from the following detailed description whenconsidered in conjunction with the drawings.

FIG. 1 depicts an example block diagram of a system 100 that can receiveinformation associated with a quality of a communication link and canprovide that information to network applications. A communicationnetwork 102 and a mobile device 104 can maintain a wirelesscommunication link to facilitate exchange of information and/or dataincluding, for example, voice information (e.g., circuit-switched and/orpacket switched voice information), e-mail, text and/or instantmessaging, streaming video, streaming audio, hypertext transfer protocol(HTTP) information associated with web-browsing, and the like. Internaland/or external network applications can be used to format transferreddata in accord with predefined standards for a particular type of data.For instance, applications can format data representing videoinformation according to a video standard, data representing musicand/or ring-tone information according to a associated music and/orring-tone standards, etc. To provide data exchange services optimizedfor a particular connection, however, such applications can requireinformation related to a quality of a communication link associated withmobile device 104 and communication network 102, including, e.g., aradio bearer associated with such network and such device.

In general, a radio bearer quality can dictate an optimal manner inwhich to facilitate data exchange services transferred via a bearerchannel. For example, if a bearer channel can support a specific datatransfer bandwidth, data exchange services can provide optimal serviceby ensuring that data transfer associated with the application occurs ata bandwidth substantially equal to the supported bandwidth. Regulatingapplication data transfer at a bandwidth higher than the supportedbandwidth can overload mobile device 104 with data (e.g., increasingpacket loss at such device and resulting in poor application service),and regulating data transfer at a bandwidth lower than the supportedbandwidth can frustrate a mobile subscriber, creating a poor impressionof service quality.

Network components (e.g., a serving general packet radio system (GPRS)node (SGSN)) associated with communication network 102 can typicallydetect and/or enforce quality parameters associated with a particularcommunication session (e.g., bandwidth, bit-rate, packet loss rate, etc.associated with a communication link). In addition, such qualityparameters can be inferred from a network architecture associated with acommunication link. For instance, if a mobile device is registered ontoa network having a third generation (3G) architecture (e.g., a universalmobile telecommunication system (UMTS) network), it can be inferred thatan associated radio bearer is of a type typical for a 3G network. As amore specific example, if a 3G network typically provides a bearerchannel having 300 kilobit per second (kbit/s) bandwidth, it can beinferred that a particular communication link to such a network issubstantially equivalent to 300 kbit/s. Additionally, if a data-capablesecond generation (2.5G) network typically provides a bearer channelhaving 150 kilobit per second (kbit/s) bandwidth, it can be inferredthat a particular communication link with a 2.5G network has a bandwidthsubstantially equivalent to 150 kbit/s. It should be appreciated thatthe foregoing example is but one of many possible combinations ofsession quality parameters applicable to the subject disclosure, andthat specific example articulated herein should not be construed so asto limit the spirit and scope of the claimed subject matter. Instead,other combinations of network components associated with communicationnetworks and session quality parameters, made known to one of skill inthe art by way of the context provided by the subject example, arecontemplated as part of the disclosure and incorporate herein.

Analysis component 106 can receive and/or extract information related toa radio bearer associated with communication network 102 and mobiledevice 104. Such information can include, for instance, an indication ofan architecture type related to communication network 102, a measuredparameter associated with the radio bearer (e.g., bandwidth, bit-rate,packet loss rate, error rate, etc.) or the like. Analysis component 106can include components proximate a communication network 102 (e.g.,network servers, access points, switches, routers, gateways, datastores, databases, etc.), components proximate mobile device 104, orseparate components, or combinations thereof. The information related toa radio bearer can be provided to analysis component 106 by othernetwork components (not depicted) associated with communication network102, such as an SGSN, a gateway GPRS node (GGSN), a radius server, awireless application protocol (WAP) gateway, or other network componentassociated with mobile data exchange, network accounting information,Internet access, inter-network communication, etc.

Analysis component 106 can transfer the information related to a radiobearer to a matching component 108. Matching component 108 can thenstore and/or submit such information to other entities (e.g., aninternal or external application content/service provider, or both, orlike entity). Such an entity, for example an external networkapplication, can then provide a service for mobile device 104 in amanner that substantially matches a characteristic of the radio bearerassociated with communication network 102 and mobile device 104. Theradio bearer information can be submitted by matching component 108, forinstance, by including such information within at least a portion of adata packet (e.g., an HTTP packet). Alternatively, matching component108 can allow other entities to access radio bearer information storedtherein in order to provide differentiated services to a mobile device(104), for instance. More specifically matching component 108 can storeinformation related to a radio bearer associated with a communicationdevice (e.g., mobile device 104) registered onto a network (e.g.,communication network 102) associated with matching component 108, andprovide access to such information to any suitable entity internaland/or external to communication network 102 (e.g., internal and/orexternal application providers, other network entities, benchmarkcomponents, testing components, etc.) Matching component 108 can includeone or more network components associated with communication network102, such as an SGSN, a gateway GPRS node (GGSN), a radius server, awireless application protocol (WAP) gateway, or other network componentassociated with mobile data exchange, network accounting information,Internet access, inter-network communication, etc.

It is to be appreciated that communication network 102 can, but is notrequired to, include a fixed IP network, such as that formed of logicalconnections to one or more remote computers such as a workstation,laptop, a server computer, a router, a personal computer, portabledevice, microprocessor-based entertainment device, peer device, or otherlike network node. Such logical connections can be facilitated via a DSLnetwork, a cable network, an optical fiber network, including a localarea network (LAN) and/or wide area network (WAN), and can furtherprovide access to global communications networks e.g. the Internet.Furthermore, access to communication network 102 can include wired (e.g.category 4 and category 5 [CAT-4 and CAT-5 respectively] etc., IEEE1394, IEEE 802.3 and the like, USB, etc.) connections or wireless (e.g.radio frequency [RF] including “Bluetooth”, 802.11 [a, b, g, n, etc.],802.16x and the like, microwave frequency, optical frequency, and thelike) connections or combinations thereof.

It is to be appreciated that communication network 102 can, but is notrequired to, include wireless access networks such as global system formobile communication (GSM) networks, time division multiple access(TDMA) networks, code division multiple access (CDMA) networks, such asIS-95 and subsequent iterations of CDMA technology, integrated digitalenhanced network (iDEN) networks, universal mobile telecommunicationsystem (UMTS) networks, UMTS VoIP networks, and other implementations offirst generation (1G), second generation (2G), advanced secondgeneration (2.5G), third generation and third generation partnershipproject (3G and 3GPP respectively) networks, subsequent wireless accesstechnologies, as well as like wireless access networks or combinationsthereof. Additionally, mobile device 102 can include, but is notrequired to include, for instance, a communication device, a multi-modedevice, a dual-mode device, a dual-mode cellular/IP device, a mobilecommunication device, a cellular device that connects to a fixed IPnetwork, a smartphone, a gaming device, a home media center, a portablemedia player, a satellite phone, a desktop device, a cellular phone, aportable gaming device, a mobile phone, a portable music player, aportable device, a laptop, a personal digital assistant, or a handheldor combinations thereof.

FIG. 2 depicts an example block diagram of a system 200 that cantransmit mobile communication link quality information to an internal orexternal application. Communication network 202 can be any suitablefixed IP or wireless access communication network as described supra.Likewise, mobile device 204 can be substantially similar to mobiledevice 104 described supra. Analysis component 206 can receive anindication of communication link quality, related to mobile device 204and communication network 202, from a communication network component(not depicted) (e.g., an SGSN serving mobile device 204). Matchingcomponent 208 can store radio bearer information associated withcommunication network 202 and mobile device 204 received at analysiscomponent 206. Additionally, matching component 208 can enable internaland/or external network application services to access such storedinformation. Alternatively, matching component 208 can submit suchinformation to an internal and/or external application (e.g., via a datapacket with such information embedded therein, infra). Such submissioncan occur via any suitable information transfer mechanism, includinge.g., circuit-switched electronic transmission, data packet routing,etc. An internal and/or external network application can include anysuitable entity internal and/or external to communication network 102(e.g., internal and/or external application providers, other networkentities, benchmark components, testing components, etc.) As a morespecific example, an entity providing e-mail services to mobile device204 can be notified of a information related to a radio bearerassociated with such device, and effectuate e-mail services at a levelcommensurate with such information (e.g., information indicating a radiobearer bandwidth can be utilized to provide e-mail services at asubstantially similar bandwidth, as indicated supra). In this manner, anentity can attempt to meet expectations of mobile service subscribesrelated to application quality of service.

Gateway component 210 can map information related to a radio bearerassociated with communication network 202 and mobile device 204 into atleast a portion of a data packet (e.g., into a header of an HTTP datapacket, or the like). Such mapping can occur via any suitable datapacket alteration or generation mechanism. For instance, a data packetreceived from mobile device 204 requesting network services can bealtered to include such mapped information, and then can be routed to anappropriate entity for filling the request. Additionally, such an entitycan provide requested services in accord with information mapped intothe data packet. As an alternative, gateway component 210 can generate adata packet and include the information related to a radio bearer intosuch generated data packet so that matching component 208 can thensubmit the packet and information to a network application.

FIG. 3 depicts an example system 300 wherein a mobile device can detect,provide, and periodically update radio bearer information in accord withaspects of the claimed subject matter. Mobile device 302 can include anysuitable mobile communication device (supra) that can resister onto acommunication network 304 (also as described supra). Detection component306 can determine information incident to a contemporaneouscommunication link related to mobile device 302 and communicationnetwork 304 (e.g., a radio bearer channel associated with such deviceand network). Such determination can be by way of a measurement of linkquality parameters (e.g., bandwidth, bit-rate, packet loss, latency, orthe like, or combinations thereof), by identifying a networkarchitecture associated with communication network 304 and inferringtypical quality parameters associated with such an architecture (e.g.,second generation (2G), 2.5G, 3G, or subsequent network architecture, orcombinations thereof), or like mechanism. Once a determination as tocontemporaneous communication link quality is made, detection componentcan provide such quality information to embedding component 308.

In an alternative scenario, detection component 306 can periodicallypoll a communication link to determine quality information relatedthereto. Determination can be made in a substantially similar fashion asdescribe above. By periodically polling a communication link, detectioncomponent can identify a substantial change in communication linkquality (e.g., caused by hand-off from one network architecture type toanother), and forward information related to the change to embeddingcomponent 308. Such information can include, for example, a newbandwidth associated with a radio bearer, a difference in bandwidtheffectuated by the change, or similar information.

Embedding component 308 can receive information related to quality of acommunication link (e.g., a radio bearer) identified by detectioncomponent 306. Such information can take the form of a particularparameter value (e.g., 300 kbit/s bandwidth, 150 kbit/s guaranteedbit-rate, 1% packet loss rate, etc.) or information identifying aparticular network architecture (e.g., an IP address of a network SGSNdedicated to a 3G network, or a 2.5G network, etc. or similar methodthat can identify a network architecture type, supra). Additionally,embedding component can format a portion of a data packet (e.g., an HTTPdata packet) so that such portion can specify communication link qualityinformation applicable to data exchange related to mobile device 302 andcommunication network 304. Alternatively, embedding component 308 cangenerate a data packet dedicated to indicating the link qualityinformation, where at least a portion of the generated data packetincludes and/or indicates such information. Embedding component 308 canthen forward such a data packet to a transmission component 310 fortransmission to an entity external to mobile device 302. Transmissioncomponent 310 can send a data packet (e.g., formatted by embeddingcomponent 308) to an external entity such as a communication network(304), device, component, node, etc., via a wired or wirelesscommunication link (supra), to apprise the entity of quality informationrelated to a communication link.

Communication network 304 can receive a formatted data packet frommobile device 302, and can forward such a data packet to a networkapplication provider 312. The formatted data packet can be interpretedand quality information embedded therein extracted by networkapplication provider 312. Such information can be used, for example, tooptimize application data exchange services in accord with acontemporaneous communication link quality (e.g., by providing astreaming video service at a bandwidth substantially equivalent to amaximum bandwidth supported by a contemporaneous communication link). Inparticular aspects, a listing component 314 can generate a list of IPaddresses associated with network SGSN components dedicated to aparticular network architecture type. The list of IP addresses ofdedicated SGSNs can be sent to network application provider 312. If adata packet sent by mobile device 302 contains such an IP address,network application provider 312 can reference the list of SGSN IPaddresses to determine whether it is dedicated to a particular networkarchitecture type. If so, a contemporaneous quality associated with acommunication link (e.g., radio bearer channel bandwidth) can beinferred from quality parameters typical for the network architecturetype. Network application provider 312 can then regulate applicationdata exchange associated with mobile device 302 accordingly (e.g., byrouting data to mobile device 302 at a bandwidth that matches a radiobearer bandwidth). Additionally, listing component 314 can periodicallyupdate the list of IP addresses of dedicated SGSNs sent to networkapplication provider 312 as network components and/or IP addresseschange.

According to additional aspects, system 300 can enable networkapplication provider 312 to alter application data services to match achange in communication link quality. If mobile device 302, as a resultof periodically polling a quality of a communication link as describedabove, transmits a formatted data packet indicating a substantial changein such quality, network application provider 312 can alter applicationdata exchange services accordingly. Consequently, system 300 can provideappropriate application data exchange parameters for a concurrentcommunication link, even if a quality of such a link changes during asession. Additionally, system 300 can optionally utilize other methods,e.g., transmission control protocol (TCP) window control, real timecontrol protocol (RTCP) flow control, or like mechanisms to managemid-session changes (e.g., a mid-session radio bearer-type change,infra).

FIG. 4 depicts a system that can identify a substantial change in theinformation related to a radio bearer and broadcast such information inaccord with various aspects of the claimed subject matter. Detection andbroadcast system 402 can include components proximate a communicationnetwork (not shown), proximate a mobile device 404, or separate fromboth, or combinations thereof. Such components can include a detectioncomponent 406, a gateway component 410, and a broadcast component 412.

Detection component 406 can detect information related to a radio bearerassociated with a mobile device 404 and a communication network. Inaddition, detection component 406 can periodically poll the radio bearerto identify substantial changes in connection quality (e.g., astypically evidenced as a result of a handover from a 3G bearer to a 2.5Gbearer, or vice versa). Furthermore, detection component 406 canassociate with an internal network component, e.g., SGSN 408, which isdedicated to a particular type of network architecture. SGSN 408 caninclude, for example, an SGSN dedicated to a UMTS, GPRS, or EDGEnetwork, or combination thereof, as described supra. Additionally, SGSN408 can be a non-dedicated SGSN that can provide service for multiplenetwork architectures (e.g., 2G/2.5G, 2G/3G, 2.5G/3G, etc.) and generatea radio access technology information element (RAT IE). The RAT IEgenerated by SGSN 408 can specify a network architecture type associatedwith a radio bearer link, specific quality information associated with aradio bearer link, or both, or specify similar connection qualityinformation related to a bearer channel. Detection component 406 canforward information related to a radio bearer associated with a mobiledevice 404 and a communication network to gateway component 410 forfurther handling.

Gateway component 410 can receive information related to a radio bearerand map it to a data packet for transmission to other entitiesincluding, for instance, components of a communication network, aninternal or external network application provider 414, or like entity.Mapped information can be included within a formatted portion of a datapacket (e.g., a data packet header) so as to specify to a subsequententity, capable of interpreting at least the formatted portion, theinformation related to the radio bearer. Such a data packet can berouted through gateway component 410 and intended for other networkpurposes (e.g., a packet transmitted by mobile device 404 evoking auniversal resource indicator (URI) to query data from a networkdatabase, application server, etc.) or generated by gateway component410 for the purpose of delivering the communication link qualityinformation. Additionally, gateway component 410 can incorporate one ormore network components including, e.g., an SGSN, a gateway GPRS node(GGSN), a radius server, a wireless application protocol (WAP) gateway,or other network component associated with mobile data exchange, networkaccounting information, Internet access, inter-network communication,etc.

Gateway component 410 can provide a formatted data packet to broadcastcomponent 412. Broadcast component 412 can contain addressinginformation related to other entities connected to a network (e.g.,network application provider 414) in order to distribute the formatteddata packet so such entities. Additionally, broadcast component cansimply transmit the formatted data packet and substantially similar datapackets periodically across the network, as a data ‘broadcast’. Entitiesoperatively disposed in data communication with detection and broadcastsystem 402 (e.g., network application provider 414) or a networkassociated therewith, can therefore receive a broadcast data packet, orsubstantially similar version, and obtain radio bearer (e.g., bandwidthinformation) information associated with mobile device 404. In such amanner network application provider 414 and other entities can obtainand store the broadcast information and utilize it if mobile device 404activates a communication service associated with such an entity.

In accord with particular aspects of the claimed subject matter, listingcomponent 416 can maintain a list of SGSN IP addresses (e.g., related toSGSN 408) dedicated to a particular network architecture type. Such alist can be updated periodically, and provided to network applicationprovider 414, or like entity. If a data packet is received specifying anIP address of a dedicated SGSN, network application provider 414 candetermine that mobile device 404 is connected via that particularnetwork architecture. Consequently, radio bearer information typicallyassociated with such architecture (e.g., 3G, 2.5G, 2G, or the like) canbe used to infer that mobile device 404 is associated with asubstantially similar bearer channel. Additionally, if networkapplication provider 414 receives a subsequent data packet related tomobile device 404 indicating an SGSN IP address dedicated to a differentnetwork architecture type, application data services can be adjusted inaccord with typical bearer attributes associated with the differentarchitecture type.

As an additional example, detection and broadcast system 402 canassociate with a network component that can generate a RAT IE messagecontaining information about a radio bearer channel (as specifiedsupra). Such a message can be received at detection component 406,incorporated into a data packet at gateway component 410, and broadcast(e.g., at broadcast component 412) so as to indicate radio bearerinformation independent of a type of SGSN (e.g., dedicated to aparticular network architecture type, or multi-type, etc.) associatedwith mobile device 404.

FIG. 5 illustrates an exemplary system 500 that can detect, update andstore communication link (e.g., a radio bearer channel) qualityinformation in accord with various aspects disclosed herein. Mobiledevice 502 can be a mobile communication device capable of exchangingdata and/or voice information over a communication network 504, asdescribed supra. Communication network 504 can be any suitable networkoperatively disposed to communicate with various electronic devices(e.g., mobile device 502) as described supra. Mobile device 502 caninclude a detection component capable of determining and/or periodicallypolling a quality of a communication link associated with mobile device502, as described herein. Such quality can be indicated via particularquality parameter values (e.g., bandwidth, bit-rate, error-rate, packetloss, etc.), a dedicated SGSN IP address and/or RAT IE messageindicating a network architecture type, or substantially similar method,or combinations thereof. Furthermore, such indication can be updated tospecify a change in the quality of a communication link (e.g., a changein bandwidth associated with a bearer channel, such as a radio bearerchannel). For example, a new bandwidth associated with a new radiobearer can be specified, a difference in bandwidth effectuated by thechange in bearer or bandwidth quality of such bearer can be specified,etc.

Embedding component 508 can format at least a portion of one or moredata packets (e.g., an HTTP data packet header) so as to specify and/orupdate a concurrent link quality as determined by detection component506. Transmission component 510 can transmit and/or broadcast at leastthe formatted portion of one or more data packets to other communicationentities (e.g., communication network 504, a service provider, anapplication, another mobile device, or like device, network, and/orservice provider, or combinations thereof). Such transmission can occur,for example, when an application is activated via a message (e.g., anHTTP message) originating at mobile device 502, when mobile device 502registers onto a network, when a change in link quality is detected bydetection component 506, or combinations of these and likecircumstances. Transmission component 510 can forward at least aformatted portion of the one or more data packets (e.g., along with orincluded within an HTTP message) to an entity related to an application,and/or to reference component 518. In a substantially similar fashion,detection component 512, gateway component 514, and broadcast component516 can also detect, prepare for transmission, broadcast and/or updateinformation related to a communication link associated with mobiledevice 502. The broadcast can be directed at a single entity, multipleentities, or broadcast across one or more networks to an unspecifiednumber of entities, and/or to reference component 518.

Reference component 518 can receive, store, and provide access to datarelated to a communication link quality (e.g., bandwidth) associatedwith mobile device 502. Such information can be updated at referencecomponent 518 over time, for instance, periodically, as a result of adetected change in communication link quality associated with mobiledevice 502 (e.g., detected by detection components 506 and/or 512) orthe like. In addition, reference component 518 can receive at least aformatted portion of a data packet (e.g., an HTTP data packet) and storeinformation specified therein (e.g., a list of IP addresses associatedwith a dedicated network SGSN, supra) related to a communication linkquality associated with mobile device 502. Furthermore, referencecomponent 518 can provide access to information stored thereon tonetwork-related entities, such as an internal and/or external networkapplication (e.g., HTTP application 520, non-HTTP application 522, orlike applications). Reference component 518 can maintain linkinformation associated with mobile devices (e.g., mobile device 502) inone or more formats recognizable by HTTP application 520 and non-HTTPapplication 522. Reference component 518, therefore, enablesapplications to obtain link information associated with devices withoutinterpreting a formatted data packet transmitted by transmissioncomponent 510 and/or broadcast component 516.

Additionally, reference component 518 can update link qualityinformation (e.g., a list of IP addresses stored therein) during amobile session, in between mobile sessions, or both, as additionalformatted data packets are received. Consequently, applications (e.g.,HTTP application 520 and/or non-HTTP application 522) can periodicallyrefer to information stored within reference component 518 to determineinformation related to communication link quality during a session, inbetween sessions, or both, and modify applications and/or applicationservices accordingly. For example, reference component 518 can update alist of IP addresses associated with dedicated network SGSNs (e.g., thatindicate a radio bearer architecture type, such as a 3G bearer, etc., asdescribe supra). More specifically, reference component 518 can add (or,for example, delete) an IP address associated with a dedicated UMTS,GPRS, or EDGE SGSN, newly assigned to such SGSN (or, for example, nolonger assigned to such SGSN), for instance, to accurately reflectconcurrent SGSNs associated with a network. It should also beappreciated that reference component 518 can exchange data with non-WAPbased applications and secure socket layer such as HTTPS or similarencryption protocol based applications as well as various other datatransfer protocols suitable for network communication.

FIG. 6 illustrates an example system 600 that provides networkarchitecture information associated with a mobile communication link(e.g., a radio bearer channel) to an application content provider inaccord with particular aspects disclosed herein. UMTS device 602 can beany suitable mobile device capable of registering onto and exchangingdata with a UMTS network (e.g., UMTS radio access network (RAN) 606).GPRS/enhanced data rate for global revolution (EDGE) device 604 can beany suitable mobile device capable of registering onto and exchangingdata with a GPRS network, an EDGE network, or both (e.g., GPRS/EDGE RAN610). UMTS RAN 606 is a 3G radio access communication network designedas a successor to the 2G global system for mobile communication (GSM)network. UMTS RAN 606 has one or more UMTS SGSNs (608) associated withit, that can provide access, routing, encoding/decoding, mobility,billing and like services for UMTS device 602 in connection with dataexchange over a GPRS core mobile communication network (of which UMTSSGSN 608, GPRS/EDGE SGSN 612, GGSN 614, and radius server 616 can form apart). GPRS/EDGE RAN 610 can include portions of the GSM core network(not depicted) and portions of an EDGE enhanced data transfer network;particularly, network components that provide access to mobile devices(e.g., GRPS/EDGE device 604) that utilize the GSM/EDGE core network(s).GPRS/EDGE SGSN 612 can act as an interface between a GSM/EDGE networkand the GPRS core network, carrying information related to GPRS/EDGEdevice 604, and more specifically can provide access, routing,encryption/decryption, mobility, billing and like services related todata exchange via a GRPS/EDGE network access point and GRPS core networkinterface.

An SGSN (e.g., UMTS SGSN 608, GPRS/EDGE SGSN 612) can typically beassociated with a radio bearer established to effectuate logicalcommunication according to specified quality parameters including, forexample, network signaling, data transport, quality managementfunctions, etc. A radio bearer can typically have different propertiesaccording to a network establishing such bearer (e.g., UMTS network,GRPS/GSM network, EDGE network, etc.) An SGSN serving a mobile devicecan typically access such radio bearer information; additionally,knowing a type of SGSN (e.g., a UMTS SGSN (608), a GRPS/EDGE SGSN (612),or the like) can typically be sufficient to infer a radio bearer aswell. Some exceptions exist, however, for non-dedicated SGSNs. If anSGSN can mediate between the GPRS core network and more than one accessnetwork, such as both a UMTS network and a GPRS/EDGE network, thensimply identifying an SGSN is insufficient to determine a type of radiobearer (e.g., UMTS or GRPS/EDGE) associated with a mobile device (e.g.,UMTS device 602 and/or GPRS/EDGE device 604). For such non-dedicatedSGSNs, further information can be required to indicate a radio bearertype. A case in which UMTS SGSN 608 and GPRS/EDGE SGSN 612 are dedicatedto a UMTS and GPRS/EDGE network is discussed first. Subsequently, a casein which UMTS SGSN 608 and/or GPRS/EDGE SGSN 612 can accommodate eithera 2/2.5G (GPRS/GSM/EDGE) network device and/or a 3G (UMTS) networkdevice is discussed.

UMTS device 602 and/or GPRS/EDGE device 604 can activate communicationservices (e.g., voice communication, data exchange with a UMTS network,data exchange with the Internet and/or an IP-based intranet, orapplications services associated with data exchange, or combinationsthereof) by initiating a packet data protocol (PDP) context message. APDP context message can be initiated, for instance, by activating (e.g.,clicking on a user interface button, etc.) a URL on a wirelessapplication protocol (WAP) browser displayed on a mobile device (notshown) (e.g., UMTS device 602, GPRS/EDGE device 604, etc.) Such PDPcontext message is received at a radio access network servicing suchdevice (e.g., UMTS RAN 606 and/or GPRS/EDGE RAN 610) and forwarded to anappropriate SGSN (e.g., UMTS SGSN 608 and/or GPRS/EDGE SGSN 612). UMTSSGSN 608 and/or GPRS/EDGE SGSN 612 can receive such PDP context messageand forward it to a gateway GSN (GGSN 614) along with an IP addressassociated with the forwarding SGSN.

A GGSN (e.g., GGSN 614) can typically include an IP address associatedwith an SGSN into a radius accounting message forwarded from GGSN 614 toa radius server (e.g., radius server 616) for accounting and billingpurposes related to a mobile device. To illustrate, a UMTS radio bearer,established by UMTS SGSN 608, can provide a relatively high bandwidthcommunication link for UMTS device 602 (as compared, for example, with acommunication link bandwidth provided by GPRS/EDGE SGSN 612 forGPRS/EDGE device 604). Such a bandwidth can form a basis for charginginformation associated with data exchange directed to UMTS device 602.Therefore, an IP address associated with an SGSN dedicated to aparticular network architecture can typically be sent to and stored at aradius server (e.g., radius server 616) to facilitate accurate chargingfunctions.

Radius server 616 can forward a radius accounting message, received fromGGSN 614 and containing an IP address associated with UMTS SGSN 608and/or GPRS/EDGE SGSN 612, to WAP gateway 618. WAP gateway 618 can actas a gateway between a mobile network and an IP network. Consequently,WAP gateway 618 can typically route, encrypt, decrypt etc. IPnetwork—based packet information (e.g., HTTP data packet protocol, etc.)to wireless-IP packet protocols (e.g., GPRS tunneling protocol (GTP)utilized by a mobile network and vice versa). WAP gateway 618,therefore, can form a basis for a UMTS device 602 and GPRS/EDGE device604 to access an IP-based network and exchange data therewith, executeapplications associated with such data exchange, etc. Additionally, WAPgateway 618 can map an IP address of an SGSN (e.g., UMTS SGSN 608 and/orGPRS/EDGE SGSN 612) received at WAP gateway 618 within a radiusaccounting message, into at least a portion of an IP-based data packet(e.g., an HTTP data packet header), and forward such data packet to acontent provider 620. It should be appreciated that WAP gateway 618might not be able to forward a packet to a non-WAP based application. Insuch a case, a data services delivery node (DSDN) (e.g., performing afunction similar to that described by reference component 518, supra)can optionally be utilized instead for non-WAP applications.Furthermore, DSDN can be utilized in conjunction with secure socketlayer, or HTTPS, protocols, which a WAP-based gateway (e.g., WAP gateway618) might be unable to process.

Content provider 620 can be any internal and/or external networkapplication provider that can facilitate data exchange formatted inconjunction with particular data applications (e.g., streaming video,e-mail, instant messaging, Internet URL access, downloading particulardata files, such as ring-tone files, music files, video files, etc.)Content provider 620 can generally establish a data exchange bandwidthfor application services. An appropriate bandwidth for applicationservices can be, for instance, a bandwidth comparable to that associatedwith a device/network connection.

To illustrate application and network connection bandwidth by example, aUMTS SGSN (608) facilitating access to a UMTS network can typicallysupport bandwidths up to 300 kbit/s. Consequently, 300 kbit/s can be anappropriate application data exchange bandwidth, for a streaming videoapplication for instance, for mobile device 602 if connected to UMTS RAN606 and UMTS SGSN 608. In contrast, GPRS/EDGE SGSN 612 can typicallyprovide a bandwidth substantially similar to 60 kbit/s and 150 kbit/srespectively for GPRS/EDGE device 604. If content provider 620 were toestablish an application data exchange bandwidth for GPRS/EDGE device604 at a typical UMTS bandwidth of 300 kbit/s, much information could belost, resulting in potentially poor application service. Additionally,if content provider 620 establishes application data exchange servicesfor UMTS device 602 at a lower bandwidth rate (e.g., typical forGPRS/EDGE connections), a subscriber can be disappointed with suchservices as well. Thus, it is beneficial for a content provider 620 tohave an indication of a communication link bandwidth between a device(602 and/or 603) and a network (606 and/or 610) to provide applicationservices at a comparable bandwidth.

System 600 can provide a radio bearer-type associated with a mobilecommunication session to content provider 620. More specifically,content provider 620 can have a list of IP addresses associated withUMTS-dedicated SGSNs (e.g., UMTS SGSN 608). Further, content provider620 can extract an IP address from a data packet formatted by WAPgateway 618. If such extracted IP address is on the list ofUMTS-dedicated IP addresses, content provider 620 can infer that an SGSN(608) serving a mobile device (602) is a UMTS-dedicated SGSN.Consequently, content provider 620 can establish application servicesrequested by a mobile device (602) (e.g., as specified within a PDPcontext message) at a bandwidth typical for a UMTS communication link.If an SGSN IP address extracted from the formatted data packet is not onthe list of UMTS-dedicated IP addresses, content provider can infer thatan SGSN (612) serving a mobile device (604) is a GPRS/EDGE SGSN.Furthermore, content provider 620 can establish application services ata bandwidth typical for a GPRS or EDGE (or some intermediary bandwidth)communication link.

In accord with additional aspects of the disclosed subject matter,system 600 can provide radio bearer-type information to a contentprovider 620 for non-dedicated SGSNs. A non-dedicated SGSN (608) canestablish a communication link between the GPRS core network and a UMTSdevice or GPRS/EDGE device. Consequently, an IP address associated withsuch an SGSN is insufficient to determine whether a device initiating aPDP context message is connected via a UMTS communication link or aGPRS/EDGE communication link. Therefore, UMTS SGSN 608 and GPRS/EDGESGSN 612 as well as GGSN 614 and radius server 616 can support a radioaccess technology information element (RAT IE) message that can specifywhether a radio bearer associated with a mobile device (602 and/or 604)is a UMTS or GPRS/EDGE bearer (e.g., as specified by third generationpartnership project (3GPP) Release 6.0).

UMTS SGSN 608 and/or GPRS/EDGE SGSN 612 can obtain and forward a RAT IEmessage specifying a radio bearer-type associated with UMTS device 602and/or GPRS/EDGE device 604 to GGSN 614. GGSN 614 can include the RAT IEmessage into protocol information transmitted between GGSN 614 andradius server 616 (e.g., a radius accounting message). Such protocolinformation containing the RAT IE message can then be forwarded fromradius server 616 to WAP gateway 618, in a substantially similar manneras described above in relation to an IP address associated with an SGSN.

WAP gateway 618 can extract a radio bearer-type from protocolinformation received from radius server 616 and map the radiobearer-type into at least a portion of a data packet transmitted tocontent provider 620 (e.g., a data packet being routed to contentprovider 620 as a result of a PDP context message generated at a device(602 and/or 604) or a data packet generated at WAP gateway, or anothernetwork component, for the purpose of indicating a radio bearer-type tocontent provider 620). Content provider 620 can receive such datapacket, or portion thereof, sent by WAP gateway 618 and extract at leasta RAT IE message incorporated therein. Further, content provider 620 canextract a radio bearer-type from such RAT IE message, and infer anappropriate bandwidth for application data services routed to UMTSdevice 602 and/or GPRS/EDGE device 604. It should be appreciated thatsystem 600 can incorporate at least a RAT IE message or an SGSN IPaddress, or both, into protocol information (e.g., a radius accountingmessage) and into one or more data packets (e.g., sent by WAP gateway618 to content provider 620) as well as like information that canindicate a radio bearer-type to an internal or external application(e.g., content provider 620).

It should be further appreciated that system 600 (at least in thededicated SGSN scenario, described above) can assist in identifying amobile device that is roaming out of a home network. For example, a listof UMTS-dedicated SGSN IP addresses maintained by content provider 620(e.g., provided by a network operator) as specified above, can furthercontain a list of GPRS/EDGE-dedicated SGSN IP addresses in addition tothe UMTS-dedicated SGSN IP addresses. An IP address associated with anSGSN, contained within a formatted data packet forwarded by WAP gateway618, for instance, can be received at content provider 620 in a mannersubstantially similar to that described above. Such IP address can bechecked against the list maintained by content provider 620 to determineif the IP address is associated with a UMTS-dedicated SGSN. If such IPaddress is not associated with a UMTS SGSN, content provider 620 canfurther check the list to determine whether the IP address is associatedwith a GPRS/EDGE-dedicated SGSN. If not, then content provider 620 canassume an SGSN supporting communication with a mobile device is notassociated with a home network, and consequently such mobile device isroaming.

FIG. 7 illustrates an example of transfer protocols transmitted betweenvarious system components in conjunction with aspects of the claimedsubject matter. GGSN 702 can be a gateway SGN typically utilized withina GPRS core network to route, encrypt, decrypt, etc., devicecommunication and/or accounting information (e.g., charging data)between one or more SGSNs serving a device(s) and mobile or fixedIP-based networks, or both, connected to GGSN 702. GGSN 702 cantypically communication with a radius server 704 by way of a radiusprotocol 706. Radius protocol 706 can generally be an authentication,authorization and accounting protocol typically used in conjunction withapplications such as network access and/or IP mobility. It can beeffective for such applications in both local and roaming scenarios.Radius protocol 706 can be utilized to transfer identificationinformation (e.g., a username and password associated with acommunication device, subscription account, subscription service(s),etc.) to radius server 704 for access to an IP network, such as theInternet, and access to application services associated with a networksubscription. Furthermore, information indicating a radio bearer-typeassociated with a mobile device (not shown) can be included within suchidentification information via radius protocol 706.

Radius server 704 can store data-transfer and like usage information(e.g., call detail records) related to data exchange. Such informationcan be used for billing purposes, and can incorporate on a radiobearer-type associated with a mobile device (e.g., a UMTS bearer, aGPRS/EDGE bearer, etc.). Such bearer-type can be indicated, forinstance, by an SGSN IP address associated with a dedicated networkSGSN, or by a RAT IE message for dedicated and/or non-dedicated networkSGSNs. Radius server 704 can receive such information, extract it from aradius protocol 706 message, and forward it to a WAP gateway 708 viaradius protocol 706. WAP gateway 708 is a gateway component thatmediates between a mobile network, and associated mobile devices,utilizing a WAP protocol and a fixed IP-based network such as theInternet or a local or wide area intranet. WAP gateway 708 can routedata between such networks similar to a proxy device, translatingInternet data into a form suitable for mobile devices (e.g., utilizing awireless markup language [WML]). WAP gateway 708 therefore can forwardrequests submitted by a mobile device to a fixed IP-based networkcomponent, and/or application content/service provider, e.g., CP/SP 710,via an HTTP protocol 712. Consequently, radio bearer-type informationspecified via radius protocol 706 and delivered by radius server 704 toWAP gateway 708, can be translated into a HTTP protocol 712 (or similarprotocol) generally utilized by an Internet-based CP/SP 710. In such amanner, bandwidth information that can be inferred from such radiobearer-type can be obtained by CP/SP 710 and utilized for applicationdata exchange services associated therewith.

Referring now to FIG. 8, an example methodology is illustrated inaccordance with the subject innovation. While, for purposes ofsimplicity of explanation, the methodologies are shown and described asa series of acts, it is to be understood and appreciated that theclaimed subject matter is not limited by the order of acts, as some actscan occur in different orders and/or concurrently with other acts fromthat shown and described herein. For example, those skilled in the artwill understand and appreciate that a methodology could alternatively berepresented as a series of interrelated states or events, such as in astate diagram. Moreover, not all illustrated acts can be required toimplement a methodology in accordance with the claimed subject matter.Additionally, it should be further appreciated that the methodologiesdisclosed hereinafter and throughout this specification are capable ofbeing stored on an article of manufacture to facilitate transporting andtransferring such methodologies to computers.

FIG. 8 illustrates an example methodology for providing mobile networklink information applicable to network transfer applications in accordwith aspects of the subject innovation. At 802, mobile network link(e.g., a radio bearer) information related to a mobile device and acommunication network is received. The mobile device can include, but isnot required to include, for instance, a communication device, amulti-mode device, a dual-mode device, a dual-mode cellular/IP device, amobile communication device, and/or similar communication devicesdescribed supra. Network link information can be associated with alogical and/or wireless connection for data exchange between the mobiledevice and a communication network. Such network can include, but is notrequired to include, a fixed IP network or a wireless access network asdescribed supra. The mobile network link information can include, forexample, quality information associated with such link (e.g., bandwidth,bit-rate, error rate, packet loss rate, jitter, etc.), networkarchitecture information associated with such link (e.g., expressed asan SGSN IP address of a dedicated SGSN, or a RAT IE message etc.), aradio bearer-type associated with such link, or similar information.

At 804, at least a portion of a data packet is updated so as to indicatethe mobile network link information. The data packet can be, forexample, an HTTP data packet; the portion of a data packet can be anHTTP packet header, for instance. In addition, the data packet can beassociated with a service request initiated at a mobile device, or canbe a packet generated specifically to bear the link information. At 806,the updated data packet is provided to a network content/serviceprovider. Such content/server provider can extract the link informationcontained within the at least a portion of a data packet to providedifferentiated services for a mobile device. More specifically,differentiated services can include at least an appropriate applicationdata exchange bandwidth for a mobile link between a mobile device and anetwork.

FIG. 9 illustrates a sample methodology for providing application dataexchange appropriate for a mobile network link in accord with thedisclosed subject matter. At 902, a data packet that specifies mobilenetwork link (e.g., radio bearer) information associated with a mobiledevice is received. More specifically, the mobile network linkinformation can relate to a communication link between a mobile deviceand a communication network. Further, the link information can include,for example, quality information, network architecture informationand/or radio bearer-type information associated with such link. The datapacket can, for instance, be associated with information routed from awireless access network, and associated device, to a fixed IP networkvia a gateway device. Alternatively, the data packet can be a packetgenerated at a gateway device for the purpose of indicating mobilenetwork link information to another entity. At 904, the mobile networklink information, specified by the data packet, is analyzed. A networkentity or entity external to a network, or both, can do such analysis toextract or otherwise obtain the mobile network link informationassociated with the mobile device. At 906, data exchange associated witha network data-transfer application is matched to a characteristicrelated to the mobile network link information. The data exchangeassociated with a network application can include, for example,streaming video, streaming audio, e-mail, downloading data from a fixedIP-based network data store, etc. In addition, the characteristicrelated to the mobile network link information can include, forinstance, a data exchange bandwidth associated with a radio bearer.

FIG. 10 illustrates a sample methodology for indicating networkarchitecture information associated with a mobile communication inaccord with aspects disclosed herein. At 1002, a PDP context message,activated at a mobile device, can be received. At 1004, an IP address ofan SGSN and/or a RAT IE message associated with a mobile device can beattached to a radius accounting (RA) message. The RA message can use astandard authentication/authorization protocol including, for example, aradius protocol. At 1006, the RA message can be forwarded to a WAPgateway. The WAP gateway can be a device capable of managing dataexchange between a mobile network using a first, mobile communicationprotocol, and a fixed IP-based network (e.g., the Internet) using asecond communication protocol, different from the first. At 1008, theWAP gateway can store an SGSN IP address and/or RAT IE messageassociated with the mobile device. At 1010, a data request message(e.g., an HTTP ‘Get’ message) can be received at the WAP gateway fromthe mobile device. The data request message can be a command deliveredby a WAP browser of a mobile device requesting information from a fixedIP-based network (e.g., the Internet) component. At 1012, the SGSN IPaddress and/or RAT IE message associated with the mobile device can bemapped into a header of an HTTP message (e.g., a data packet). At 1014,at least the mapped portion of the HTTP message can be forwarded to anapplication content/service provider. Such content/service provider canutilize the SGSN IP address and/or RAT IE message to provide applicationdata exchange to a mobile device at an appropriate rate for a particularmobile link.

Referring now to FIG. 11, there is illustrated a block diagram of acomputer operable to provide networking and communication capabilitiesbetween a wired or wireless communication network and a server and/orcommunication device. While shown through use of a computer or computingcomponents, it is understood that the claimed subject matter can beimplemented as a method, apparatus, or article of manufacture usingstandard programming and/or engineering techniques to produce software,firmware, hardware, or combinations thereof to control a computingdevice, such as a mobile handset, to implement the disclosed subjectmatter. The term “article of manufacture” as used herein is intended toencompass a computer program accessible from any suitablecomputer-readable device, carrier, or media. For example, computerreadable media can include but is not limited to magnetic storagedevices (e.g., hard disk, floppy disk, magnetic strips . . . ), opticaldisks (e.g., compact disk (CD), digital versatile disk (DVD) . . . ),smart cards, SIM cards, and flash memory devices (e.g., card, stick, keydrive . . . ). Additionally it should be appreciated that a carrier wavecan be employed to carry computer-readable electronic data such as thoseused in transmitting and receiving electronic mail or in accessing anetwork such as the Internet or a local area network (LAN). Of course,those skilled in the art will recognize many modifications can be madeto this configuration without departing from the scope or spirit of theclaimed subject matter.

In order to provide additional context for various aspects of theclaimed subject matter, FIG. 11 and the following discussion areintended to provide a brief, general description of a suitable computingenvironment 1100 in which the various aspects described herein can beimplemented. While the description above is in the general context ofcomputer-executable instructions that can run on one or more computers,those skilled in the art will recognize that the claimed subject matteralso can be implemented in combination with other program modules and/oras a combination of hardware and software.

Generally, program modules include routines, programs, components, datastructures, etc., that perform particular tasks or implement particularabstract data types. Moreover, those skilled in the art will appreciatethat the inventive methods can be practiced with other computer systemconfigurations, including single-processor or multiprocessor computersystems, minicomputers, mainframe computers, as well as personalcomputers, hand-held computing devices, microprocessor-based orprogrammable consumer electronics, and the like, each of which can beoperatively coupled to one or more associated devices.

The illustrated aspects of the claimed subject matter can also bepracticed in distributed computing environments where certain tasks areperformed by remote processing devices that are linked through acommunications network. In a distributed computing environment, programmodules can be located in both local and remote memory storage devices.

A computer typically includes a variety of computer-readable media.Computer-readable media can be any available media that can be accessedby the computer and includes both volatile and non-volatile media,removable and non-removable media. By way of example, and notlimitation, computer-readable media can comprise computer storage mediaand communication media. Computer storage media includes both volatileand non-volatile, removable and non-removable media implemented in anymethod or technology for storage of information such ascomputer-readable instructions, data structures, program modules orother data. Computer storage media includes, but is not limited to, RAM,ROM, EEPROM, flash memory or other memory technology, CD-ROM, digitalvideo disk (DVD) or other optical disk storage, magnetic cassettes,magnetic tape, magnetic disk storage or other magnetic storage devices,or any other medium which can be used to store the desired informationand which can be accessed by the computer.

Communication media typically embodies computer-readable instructions,data structures, program modules or other data in a modulated datasignal such as a carrier wave or other transport mechanism, and includesany information delivery media. The term “modulated data signal” means asignal that has one or more of its characteristics set or changed insuch a manner as to encode information in the signal. By way of example,and not limitation, communication media includes wired media such as awired network or direct-wired connection, and wireless media such asacoustic, RF, infrared and other wireless media. Combinations of the anyof the above should also be included within the scope of communicationmedia derived from computer-readable media and capable of subsequentlypropagating through electrically conductive media, (e.g., such as asystem bus, microprocessor, data port, and the like) and/ornon-electrically conductive media (e.g., in the form of radio frequency,microwave frequency, optical frequency and similar electromagneticfrequency modulated data signals).

With reference again to FIG. 11, the exemplary environment 1100 forimplementing various aspects includes a computer 1102, the computer 1102including a processing unit 1104, a system memory 1106 and a system bus1108. The system bus 1108 couples system components including, but notlimited to, the system memory 1106 to the processing unit 1104. Theprocessing unit 1104 can be any of various commercially availableprocessors, such a single core processor, a multi-core processor, or anyother suitable arrangement of processors. The system bus 1108 can be anyof several types of bus structure that can further interconnect to amemory bus (with or without a memory controller), a peripheral bus, anda local bus using any of a variety of commercially available busarchitectures. The system memory 1106 can include read-only memory(ROM), random access memory (RAM), high-speed RAM (such as static RAM),EPROM, EEPROM, and/or the like. Additionally or alternatively, thecomputer 1102 can include a hard disk drive, upon which programinstructions, data, and the like can be retained. Moreover, removabledata storage can be associated with the computer 1102. Hard disk drives,removable media, etc. can be communicatively coupled to the processingunit 1104 by way of the system bus 1108.

The system memory 1106 can retain a number of program modules, such asan operating system, one or more application programs, other programmodules, and program data. All or portions of an operating system,applications, modules, and/or data can be, for instance, cached in RAM,retained upon a hard disk drive, or any other suitable location. A usercan enter commands and information into the computer 1102 through one ormore wired/wireless input devices, such as a keyboard, pointing andclicking mechanism, pressure sensitive screen, microphone, joystick,stylus pen, etc. A monitor or other type of interface can also beconnected to the system bus 1108.

The computer 1102 can operate in a networked environment using logicalconnections via wired and/or wireless communications to one or moreremote computers, phones, or other computing devices, such asworkstations, server computers, routers, personal computers, portablecomputers, microprocessor-based entertainment appliances, peer devicesor other common network nodes, etc. The computer 1102 can connect toother devices/networks by way of antenna, port, network interfaceadaptor, wireless access point, modem, and/or the like.

The computer 1102 is operable to communicate with any wireless devicesor entities operatively disposed in wireless communication, e.g., aprinter, scanner, desktop and/or portable computer, portable dataassistant, communications satellite, any piece of equipment or locationassociated with a wirelessly detectable tag (e.g., a kiosk, news stand,restroom), and telephone. This includes at least WiFi and Bluetooth™wireless technologies. Thus, the communication can be a predefinedstructure as with a conventional network or simply an ad hoccommunication between at least two devices.

WiFi, or Wireless Fidelity, allows connection to the Internet from acouch at home, a bed in a hotel room, or a conference room at work,without wires. WiFi is a wireless technology similar to that used in acell phone that enables such devices, e.g., computers, to send andreceive data indoors and out, anywhere within the range of a basestation. WiFi networks use radio technologies called IEEE 802.11 (a, b,g, etc.) to provide secure, reliable, fast wireless connectivity. A WiFinetwork can be used to connect computers to each other, to the Internet,and to wired networks (which use IEEE 802.3 or Ethernet). WiFi networksoperate in the unlicensed 2.4 and 5 GHz radio bands, at an 11 Mbps(802.11a) or 54 Mbps (802.11b) data rate, for example, or with productsthat contain both bands (dual band), so the networks can providereal-world performance similar to the basic 10BaseT wired Ethernetnetworks used in many offices.

Now turning to FIG. 12, such figure depicts a GSM/GPRS/IP multimedianetwork architecture 1200 that includes a GSM core network 1201, a GPRSnetwork 1230 and an IP multimedia network 1238. The GSM core network1201 includes a Mobile Station (MS) 1202, at least one Base TransceiverStation (BTS) 1204 and a Base Station Controller (BSC) 1206. The MS 1202is physical equipment or Mobile Equipment (ME), such as a mobile phoneor a laptop computer that is used by mobile subscribers, with aSubscriber identity Module (SIM). The SIM includes an InternationalMobile Subscriber Identity (IMSI), which is a unique identifier of asubscriber. The MS 1202 includes an embedded client 1202 a that receivesand processes messages received by the MS 1202. The embedded client 1202a can be implemented in JAVA and is discuss more fully below.

The embedded client 1202 a communicates with an application 1202 b thatprovides services and/or information to an end user. One example of theapplication can be navigation software that provides near real-timetraffic information that is received via the embedded client 1202 a tothe end user. The navigation software can provide road conditions,suggest alternate routes, etc. based on the location of the MS 1202.Those of ordinary skill in the art understand that there are manydifferent methods and systems of locating an MS 1202.

Alternatively, the MS 1202 and a device 1202 c can be enabled tocommunicate via a short-range wireless communication link, such asBLUETOOTH. For example, a BLUETOOTH SIM Access Profile can be providedin an automobile (e.g., device 1202 c) that communicates with the SIM inthe MS 1202 to enable the automobile's communications system to pullinformation from the MS 1202. The BLUETOOTH communication system in thevehicle becomes an “embedded phone” that employs an antenna associatedwith the automobile. The result is improved reception of calls made inthe vehicle. As one of ordinary skill in the art would recognize, anautomobile is one example of the device 1202 c. There can be an endlessnumber of devices 1202 c that use the SIM within the MS 1202 to provideservices, information, data, audio, video, etc. to end users.

The BTS 1204 is physical equipment, such as a radio tower, that enablesa radio interface to communicate with the MS. Each BTS can serve morethan one MS. The BSC 1206 manages radio resources, including the BTS.The BSC can be connected to several BTSs. The BSC and BTS components, incombination, are generally referred to as a base station (BSS) or radioaccess network (RAN) 1203.

The GSM core network 1201 also includes a Mobile Switching Center (MSC)1208, a Gateway Mobile Switching Center (GMSC) 1210, a Home LocationRegister (HLR) 1212, Visitor Location Register (VLR) 1214, anAuthentication Center (AuC) 1218, and an Equipment Identity Register(EIR) 1216. The MSC 1208 performs a switching function for the network.The MSC also performs other functions, such as registration,authentication, location updating, handovers, and call routing. The GMSC1210 provides a gateway between the GSM network and other networks, suchas an Integrated Services Digital Network (ISDN) or Public SwitchedTelephone Networks (PSTNs) 1220. In other words, the GMSC 1210 providesinterworking functionality with external networks.

The HLR 1212 is a database or component(s) that comprises administrativeinformation regarding each subscriber registered in a corresponding GSMnetwork. The HLR 1212 also includes the current location of each MS. TheVLR 1214 is a database or component(s) that contains selectedadministrative information from the HLR 1212. The VLR containsinformation necessary for call control and provision of subscribedservices for each MS currently located in a geographical area controlledby the VLR. The HLR 1212 and the VLR 1214, together with the MSC 1208,provide the call routing and roaming capabilities of GSM. The AuC 1216provides the parameters needed for authentication and encryptionfunctions. Such parameters allow verification of a subscriber'sidentity. The EIR 1218 stores security-sensitive information about themobile equipment.

A Short Message Service Center (SMSC) 1209 allows one-to-one ShortMessage Service (SMS) messages to be sent to/from the MS 1202. A PushProxy Gateway (PPG) 1211 is used to “push” (e.g., send without asynchronous request) content to the MS 1202. The PPG 1211 acts as aproxy between wired and wireless networks to facilitate pushing of datato the MS 1202. A Short Message Peer to Peer (SMPP) protocol router 1213is provided to convert SMS-based SMPP messages to cell broadcastmessages. SMPP is a protocol for exchanging SMS messages between SMSpeer entities such as short message service centers. It is often used toallow third parties, e.g., content suppliers such as news organizations,to submit bulk messages.

To gain access to GSM services, such as speech, data, and short messageservice (SMS), the MS first registers with the network to indicate itscurrent location by performing a location update and IMSI attachprocedure. The MS 1202 sends a location update including its currentlocation information to the MSC/VLR, via the BTS 1204 and the BSC 1206.The location information is then sent to the MS's HLR. The HLR isupdated with the location information received from the MSC/VLR. Thelocation update also is performed when the MS moves to a new locationarea. Typically, the location update is periodically performed to updatethe database as location-updating events occur.

The GPRS network 1230 is logically implemented on the GSM core networkarchitecture by introducing two packet-switching network nodes, aserving GPRS support node (SGSN) 1232, a cell broadcast and a GatewayGPRS support node (GGSN) 1234. The SGSN 1232 is at the same hierarchicallevel as the MSC 1208 in the GSM network. The SGSN controls theconnection between the GPRS network and the MS 1202. The SGSN also keepstrack of individual MS's locations and security functions and accesscontrols.

A Cell Broadcast Center (CBC) 1233 communicates cell broadcast messagesthat are typically delivered to multiple users in a specified area. CellBroadcast is one-to-many geographically focused service. It enablesmessages to be communicated to multiple mobile phone customers who arelocated within a given part of its network coverage area at the time themessage is broadcast.

The GGSN 1234 provides a gateway between the GPRS network and a publicpacket network (PDN) or other IP networks 1236. That is, the GGSNprovides interworking functionality with external networks, and sets upa logical link to the MS through the SGSN. When packet-switched dataleaves the GPRS network, it is transferred to an external TCP-IP network1236, such as an X.25 network or the Internet. In order to access GPRSservices, the MS first attaches itself to the GPRS network by performingan attach procedure. The MS then activates a packet data protocol (PDP)context, thus activating a packet communication session between the MS.the SGSN, arc the GGSN.

In a GSM/GPRS network, GPRS services and GSM services can be used inparallel. The MS can operate in one three classes: class A, class B, andclass C. A class A MS can attach to the network for both GPRS servicesand GSM services simultaneously. A class A MS also supports simultaneousoperation of GPRS services and GSM services. For example, class Amobiles can receive GSM voice/data/SMS calls and GPRS data calls at thesame time. A class B MS can attach to the network for both GPRS servicesand GSM services simultaneously. However, a class B MS does not supportsimultaneous operation of the GPRS services and GSM services. That is, aclass B MS can only use one of the two services at a given time. A classC MS can attach for only one of the GPRS services and GSM services at atime. Simultaneous attachment and operation of GPRS services and GSMservices is not possible with a class C MS.

A GPRS network 1230 can be designed to operate in three networkoperation modes (NOM1, NOM2 and NOM3). A network operation mode of aGPRS network is indicated by a parameter in system information messagestransmitted within a cell. The system information messages dictates a MSwhere to listen for paging messages and how signal towards the network.The network operation mode represents the capabilities of the GPRSnetwork. In a NOM1 network, a MS can receive pages from a circuitswitched domain (voice call) when engaged in a data call. The MS cansuspend the data call or take both simultaneously, depending on theability of the MS. In a NOM2 network, a MS cannot receive pages from acircuit switched domain when engaged in a data call, since the MS isreceiving data and is not listening to a paging channel. In a NOM3network, a MS can monitor pages for a circuit switched network whilereceived data and vise versa.

The IP multimedia network 1238 was introduced with 3GPP Release 5, andincludes an IP multimedia subsystem (IMS) 1240 to provide richmultimedia services to end users. A representative set of the networkentities within the IMS 1240 are a call/session control function (CSCF),a media gateway control function (MGCF) 1246, a media gateway (MGW)1248, and a master subscriber database, called a home subscriber server(HSS) 1250. The HSS 1250 can be common to the GSM network 1201, the GPRSnetwork 1230 as well as the IP multimedia network 1238.

The IP multimedia system 1240 is built around the call/session controlfunction, of which there are three types: an interrogating CSCF (I-CSCF)1243, a proxy CSCF (P-CSCF) 1242, and a serving CSCF (S-CSCF) 1244. TheP-CSCF 1242 is the MS's first point of contact with the IMS 1240. TheP-CSCF 1242 forwards session initiation protocol (SIP) messages receivedfrom the MS to an SIP server in a home network (and vice versa) of theMS. The P-CSCF 1242 can also modify an outgoing request according to aset of rules defined by the network operator (for example, addressanalysis and potential modification).

The I-CSCF 1243 forms an entrance to a home network and hides the innertopology of the home network from other networks and providesflexibility for selecting an S-CSCF. The I-CSCF 1243 can contact asubscriber location function (SLF) 1245 to determine which HSS 1250 touse for the particular subscriber, if multiple HSSs 1250 are present.The S-CSCF 1244 performs the session control services for the MS 1202.This includes routing originating sessions to external networks androuting terminating sessions to visited networks. The S-CSCF 1244 alsodecides whether an application server (AS) 1252 is required to receiveinformation on an incoming SIP session request to ensure appropriateservice handling. This decision is based on information received fromthe HSS 1250 (or other sources, such as an application server 1252). TheAS 1252 also communicates to a location server 1256 (e.g., a GatewayMobile Location Center (GMLC)) that provides a position (e.g.,latitude/longitude coordinates) of the MS 1202.

The HSS 1250 contains a subscriber profile and keeps track of which corenetwork node is currently handling the subscriber. It also supportssubscriber authentication and authorization functions (AAA). In networkswith more than one HSS 1250, a subscriber location function providesinformation on the HSS 1250 that contains the profile of a givensubscriber.

The MGCF 1246 provides interworking functionality between SIP sessioncontrol signaling from the IMS 1240 and ISUP/BICC call control signalingfrom the external GSTN networks (not shown). It also controls the mediagateway (MGW) 1248 that provides user-plane interworking functionality(e.g., converting between AMR- and PCM-coded voice). The MGW 1248 alsocommunicates with other IP multimedia networks 1254.

Appendix A discloses various aspects of the claimed subject matter andis hereby incorporated into the subject specification. Consequently,terms defined in the subject specification apply with equal force tosubstantially similar terms included within Appendix A.

What has been described above includes examples of the claimed subjectmatter. It is, of course, not possible to describe every conceivablecombination of components or methodologies for purposes of describingthe claimed subject matter, but one of ordinary skill in the art canrecognize that many further combinations and permutations of such matterare possible. Accordingly, the claimed subject matter is intended toembrace all such alterations, modifications and variations that fallwithin the spirit and scope of the appended claims. Furthermore, to theextent that the term “includes” is used in either the detaileddescription or the claims, such term is intended to be inclusive in amanner similar to the term “comprising” as “comprising” is interpretedwhen employed as a transitional word in a claim.

What is claimed is:
 1. A system, comprising: a processor; and a memorythat stores executable instructions that, when executed by theprocessor, facilitate performance of operations, comprising: determiningnetwork architecture type information representing a networkarchitecture type associated with a radio bearer device employed for acommunication session between a network device of a communicationnetwork and a mobile device; and sending the network architecture typeinformation to a content provider device providing a service via thecommunication session to the mobile device, wherein the networkarchitecture type information enables the content provider device todetermine a transmission bandwidth supported by the network architecturetype and customize content for the service to be supplied to the mobiledevice at a data exchange rate that is a function of the transmissionbandwidth determined to be supported by the radio bearer device.
 2. Thesystem of claim 1, further comprising generating respective lists ofInternet Protocol addresses associated with radio bearer devicesassociated with network architecture types.
 3. The system of claim 2,wherein the network architecture type information further comprises therespective lists of Internet Protocol addresses associated with theradio bearer devices associated with the network architecture types. 4.The system of claim 3, wherein the network architecture type informationfurther comprises an Internet Protocol address associated with the radiobearer device.
 5. The system of claim 1, wherein the networkarchitecture type information further comprises radio access technologyinformation that indicates the network architecture type.
 6. The systemof claim 1, wherein the content provider device is a video streamserver.
 7. The system of claim 1, wherein the service comprises deliveryof a video stream.
 8. A method, comprising: determining, by a deviceincluding a processor, network architecture type informationrepresenting a network architecture type associated with a radio bearerdevice employed for a communication session between a network device ofa communication network and a mobile device; and sending, by the device,the network architecture type information to a content provider deviceproviding a service to the mobile device using the communicationsession, wherein the network architecture type information enables thecontent provider device to determine a transmission bandwidth supportedby the network architecture type and customize content for the serviceto be supplied to the mobile device at a data exchange rate that is afunction of the transmission bandwidth determined to be supported by theradio bearer device.
 9. The method of claim 8, further comprisinggenerating respective lists of Internet Protocol addresses associatedwith radio bearer devices associated with network architecture types.10. The method of claim 9, wherein the network architecture typeinformation further comprises the respective lists of Internet Protocoladdresses associated with the radio bearer devices associated with thenetwork architecture types.
 11. The method of claim 10, wherein thenetwork architecture type information further comprises an InternetProtocol address associated with the radio bearer device.
 12. The methodof claim 8, wherein the network architecture type information furthercomprises radio access technology information that indicates the networkarchitecture type.
 13. The method of claim 8, wherein the contentprovider device is a video stream server that delivers a video stream tothe mobile device.
 14. The method of claim 8, wherein the servicedelivers a video stream to the mobile device.
 15. A machine-readablestorage medium, comprising executable instructions that, when executedby a processor, facilitate performance of operations, comprising:determining network architecture type information representing a networkarchitecture type associated with a radio bearer device employed for acommunication session between a network device of a communicationnetwork and a mobile device; and sending the network architecture typeinformation to a content provider device providing a service over thecommunication session to the mobile device, wherein the networkarchitecture type information enables the content provider device todetermine a transmission bandwidth supported by the network architecturetype and customize content for the service to be supplied to the mobiledevice at a data exchange rate that is a function of the transmissionbandwidth.
 16. The machine-readable storage medium of claim 15, whereinthe operations further comprise generating respective lists of InternetProtocol addresses associated with radio bearer devices associated withnetwork architecture types.
 17. The machine-readable storage medium ofclaim 16, wherein the network architecture type information furthercomprises the respective lists of Internet Protocol addresses associatedwith the radio bearer devices associated with the network architecturetypes.
 18. The machine-readable storage medium of claim 17, wherein thenetwork architecture type information further comprises an InternetProtocol address associated with the radio bearer device.
 19. Themachine-readable storage medium of claim 15, wherein the networkarchitecture type information further comprises radio access technologyinformation that indicates the network architecture type.
 20. Thecomputer-readable storage device of claim 15, wherein the contentprovider device is a video stream server and the service is transmissionof a video stream to the mobile device.